Repository navigation
chore(security): add ReversingLabs malware scan workflow - #1712
Merged
Merged
Conversation
Contributor
Author
|
@auth0/project-dx-sdks-engineer-codeowner please review the files in the PR. This automated security-hardening workflow is untested in this repo — before merging, confirm it triggers and passes (and is not silently ignoring failures); do not merge on a green result alone. |
Contributor
Author
|
An internal service ticket has been filed for the owning team to review and merge this PR. |
Download each published release archive and scan it with the rl-scan action, once per OS and architecture. The scan job runs after GoReleaser and nothing depends on it, so a failed scan does not block the release.
developerkunal
enabled auto-merge (squash)
October 19, 2026 19:04
ramya18101
reviewed
Oct 21, 2026
| # Caller pattern (single archive; release.yml uses a matrix of all six): | ||
| # jobs: | ||
| # release-and-scan: | ||
| # rl-scan: |
Contributor
There was a problem hiding this comment.
Can we remove this pattern examples, as we already added jobs in here
ramya18101
approved these changes
Oct 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🔧 Changes
Adds a ReversingLabs malware scan of the released binaries.
.github/workflows/rl.ymlis a reusable workflow. It downloads one published release archive (auth0-cli_<version>_<suffix>) from the GitHub release and scans it with therl-scanaction fromauth0/devsecops-tooling. The job fails unless the scan status issuccess..github/workflows/release.ymlgets a newrl-scanjob that runs after GoReleaser and callsrl.ymlonce for each of the six archives: Darwin, Linux and Windows, on arm64 and x86_64.release-beta.yml) are not scanned.The scan needs the eight RL and ProdSec org secrets to be available to this repository, and the AWS role behind
PRODSEC_TOOLS_ARNmust trust it.🔬 Testing
This has not run end to end yet, because it needs the org secrets and the AWS trust for this repository. It runs on the next stable release tag.
📝 Checklist